docs: adding superset dockerfile patch article - #385
Conversation
|
Thanks for the pull request, @DeimerM! This repository is currently maintained by Once you've gone through the following steps feel free to tag them in a comment and let them know that your changes are ready for engineering review. 🔘 Get product approvalIf you haven't already, check this list to see if your contribution needs to go through the product review process.
🔘 Provide contextTo help your reviewers and other members of the community understand the purpose and larger context of your changes, feel free to add as much of the following information to the PR description as you can:
🔘 Get a green buildIf one or more checks are failing, continue working on your changes until this is no longer the case and your build turns green. DetailsWhere can I find more information?If you'd like to get more details on all aspects of the review process for open source pull requests (OSPRs), check out the following resources: When can I expect my changes to be merged?Our goal is to get community contributions seen and reviewed as efficiently as possible. However, the amount of time that it takes to review and merge a PR can vary significantly based on factors such as:
💡 As a result it may take up to several weeks or months to complete a review and merge your PR. |
Description
This article explains how to customize the Apache Superset container build process using the
superset-dockerfilepatch in an Open edX Aspects environment. It outlines where to define the patch within your custom inline plugin configuration and notes that these modifications take effect when theaspects-supersetimage is built. By appending custom Dockerfile instructions—such as installing extra Python dependencies or overriding the defaultCMDandENTRYPOINT—to the final image layer, developers can easily tailor the Superset environment to their specific deployment needs.